User's Guide
- Get the latest level of LAN driver updates for your operating system to
ensure that your code is at the latest level.
- Be sure that your IBM Turbo 16/4 Token-Ring PC Card 2 has already been
installed in your computer. If it has not, follow the instructions in Inserting and Removing the PC Card.
- Get the driver for your environment. There are three places to find
the driver. If you have a Web connection, we recommend the first one
listed here. All three methods will place the driver in a directory
according to the structure in Table 1.
- Method A: Get the driver from a software package on the IBM
Networking Hardware Division home page on the Web. This will ensure
that you get the latest driver. Go to
x:\startcd.HTM (where x is your CD-ROM drive).
Select IBM Networking Web site -- product support.
Select Downloads and choose the appropriate software package for
your environment. Run the package to expand the files.
| Note: | You can also access the Web site directly at
www.networking.ibm.com/support
|
- Method B: Use the driver shipped on this CD-ROM directly with your
network operating system's installation software.
- Method C: Get the driver from a software package shipped on this
CD-ROM. Point your Web browser to
x:\startcd.HTM (where x is your CD-ROM drive).
Select CD-ROM -- product support. Select
Downloads and choose the appropriate software package for your
environment. Run the package to expand the files.
- Install the driver. Use Table 2 and Table 3 to find the location of the installation
instructions for your environment. It is recommended that you install
the latest service pack for your operating environment before installing the
PC Card software.
Table 1. Driver File Directory Structure
| Operating System
| Directory
|
| Windows 9x
| \ (root)
|
| Windows NT
| \ (root)
|
| Windows 2000
| \ (root)
|
| Novell NetWare Server and Client
| \NOVELL\NETWARE
|
| Novell NetWare DOS Requester (16-bit)
| \NOVELL\DOS
|
| OS/2
| \ (root)
|
| DOS
| \DOS
|
| Windows for Workgroups
| \WFW
|
If you are using one of the environments listed in Table 2, you will not use LANAID.
Where to Find the Installation Instructions for Your Environment
Table 2. Do not use LANAID to configure your machine
If you are using the environment listed in Table 3, you will use LANAID to configure your machine. Even
though the network operating system appears to fully install and configure the
device driver, it is highly recommended that you run LANAID to ensure that the
PC Card is appropriately configured.
Table 3. Use LANAID to configure your machine
| Note: | If you are operating in a server environment, you might not get support from
your hardware or network operating system manufacturers.
|
IBMTOKEN.LAN is used in both the NetWare Server and Client
environments. In order to use this driver, your system must enable the
card by loading: Socket Services, Card Services, and
CS20TOK.EXE. POINTTR.EXE is not supported with
IBMTOKEN.LAN.
If Card Services on your system is earlier than version 5.00, enter
the following parameter when you load the driver: MEM1=<SRAM Address>
LOAD IBMTOKEN.LAN FRAME=TOKEN-RING MEM1=C8000
If you do not put this parameter on the driver load line, you will be
prompted for this parameter every time you load the driver.
If your Card Services is version 5.00 or higher, you do not need to
worry about this parameter.
CS20TOK.EXE is a small software program that configures the PC
Card socket controller to allocate resources (memory, I/O Ports, interrupts,
DMA channels, and power) to PCMCIA cards. Once CS20TOK.EXE has
run successfully, the PCMCIA Token-Ring card is ready to operate and looks
much like any ISA Token-Ring adapter.
Generally, enabling a card is done by loading CS20TOK.EXE in
CONFIG.SYS, AUTOEXEC.BAT, or at a DOS prompt.
For a complete list of CS20TOK.EXE parameters, you can enter the
following at a DOS prompt:
CS20TOK /? or CS20TOK /h
Examples:
In autoexec.bat:
cs20tok sa mmio=d000 sram=d000,4 rs=16 irq=a io=0a20
In config.sys:
device=c:\cs20tok.exe sa mmio=d000 sram=d000,4 rs=16 irq=a io=0a20
Both set the card in slot 1 (sa) to an 8-KB memory region based at
X'0D0000', with the card operating in enhanced mode. The card
is assigned port X'0A20', interrupt vector X'A' (10 decimal),
and Token-Ring speed (rs) will be 16 Mbps. The program runs, then
sounds two ascending beeps indicating successful operation. The card is
now enabled and ready for the driver to be loaded.
Here is an example of using CS20TOK.EXE with two adapters:
cs20tok sa mmio=d000 sram=d000,4 rs=16 irq=a io=0a20 pri
cs20tok sb mmio=c800 sram=c800,4 rs=16 irq=9 io=0a24 alt
Before you start this installation, get the latest level of
patches for NetWare 3.12 from Novell. The current level is
IntraNetWare Support Pack Version 5.0 from the Novell support Web site
at support.novell.com. You will install the patches
during the following procedure.
If the Novell NetWare server is not on your computer, use the following
instructions. If it is on your computer, go to the instructions on page
***.
Server Driver Installation in New NetWare 3.12 Server
Changes from the usual NetWare installation are necessary because this
driver is written to a new specification level that requires new NetWare
loadable modules (NLMs). The installation program is not aware of this,
though, and these NLMs must be loaded during installation of the server device
driver and after the server installation.
- Create a diskette containing the extracted files from the
NETWARE.EXE package file on the IBM Turbo 16/4 Token-Ring PC Card 2
CD-ROM.
- Refer to Novell's Installation and Upgrade manual for
installation instructions. Follow the procedure for the installation of
Novell NetWare 3.12 until the section titled "Load LAN Drivers" is
next.
- Insert the diskette that you created in step 1 into drive A. Enter
the following commands at the server prompt:
LOAD A:\NOVELL\NETWARE\NBI31X.NLM
LOAD A:\NOVELL\NETWARE\MSM31X.NLM
LOAD A:\NOVELL\NETWARE\TOKENTSM.NLM
| Note: | A message referring to protected-mode BIOS access might appear
before installation of Novell patches. It is for information only and
can be ignored.
|
- Load the server device driver. Enter the following command at the
server prompt:
LOAD X:\NOVELL\NETWARE\IBMTOKEN.LAN DATARATE=M16
In server environments, the DataRate should be set to M16 or M4, and
clients should be set to Auto. The default is Auto.
- Follow the instructions in the Novell manual, beginning with "Bind the
Protocol to the LAN Driver" and continue until you are in the File Server
STARTUP.NCF File panel.
- In addition to the instructions in the Novell manual, add the following
line to STARTUP.NCF:
Set Minimum Packet Receive Buffers = 48
| Note: | Increase the minimum packet receive buffers by 48 for each additional adapter
that is installed.
|
- Perform the instructions in "Create an AUTOEXEC.NCF file" in the
Novell manual. Add the following lines to the AUTOEXEC.NCF file
immediately after the IPX INTERNAL NET statement (replace
C:\SERVER.312\ with the location of the NetWare server
program):
LOAD C:\SERVER.312\NBI31X.NLM
LOAD C:\SERVER.312\MSM31X.NLM
LOAD C:\SERVER.312\TOKENTSM.NLM
LOAD C:\SERVER.312\IBMTOKEN.LAN NAME=IBMLS1 DATARATE=M16
BIND IPX TO IBMLS1 NET=<unique net number>
Make sure that the line containing IBMTOKEN.LAN has the complete
path name.
Notes:
- See Novell NetWare Server Driver Messages for a complete list of parameters that you can specify on
the LOAD IBMTOKEN command in the AUTOEXEC.NCF file.
- If you experience any problems after loading the Novell NLM files, contact
Novell to ensure that you have the current version of these files.
Press Esc and answer Yes to save the new file to
disk. Press Esc again to return to the server
console.
- Shut down your server by entering down and then entering
exit from the server prompt.
- Make sure that the diskette that you created in step 1 is inserted in
drive A. Enter the following commands at the server prompt. You
might be prompted to perform a file overwrite; it is OK to overwrite these
files.
COPY A:\NOVELL\NETWARE\NBI31X.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\MSM31X.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\IBMTOKEN.LAN C:\SERVER.312
COPY A:\NOVELL\NETWARE\IBMTOKEN.LDI C:\SERVER.312
- Go to the Novell server directory and enter server at the DOS
prompt to restart the server.
- Install the patches obtained earlier now. Make sure to select the
v3.31 ODI LAN Updates for Hardware if given the opportunity.
- Installation is now complete.
Check for the following conditions to determine whether the adapter is
working correctly and whether installation is complete:
- The device driver files are loading successfully.
- There are no error messages.
If you experience problems, go to Appendix B. Problem Determination.
For information concerning NetWare server error messages, see Novell NetWare Server Driver Parameters.
Server Driver Installation in
Existing NetWare 3.12 Server
If Novell NetWare is on your computer, perform the following steps to
install the adapter server device driver.
- Create a diskette containing the extracted files from the
NETWARE.EXE file on the IBM Turbo 16/4 Token-Ring PC Card 2
CD-ROM.
- Install the patches obtained earlier now. Make sure to select the
v3.31 ODI LAN Updates for Hardware if given the opportunity.
Return to the server console when the installation is complete.
- Make sure that the diskette you created in step 1 has been inserted in
drive A. Enter the following commands at the server prompt. You
might be prompted to perform a file overwrite; it is OK to overwrite these
files.
COPY A:\NOVELL\NETWARE\NBI31X.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\MSM31X.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\IBMTOKEN.LAN C:\SERVER.312
COPY A:\NOVELL\NETWARE\IBMTOKEN.LDI C:\SERVER.312
| Note: | If you experience any problems after loading the Novell NLM files, check the
Novell Web site to ensure that you have the current version of these
files.
|
- In the directory where Novell is installed on your hard disk, enter
server at the DOS prompt to start the server.
- At the server console prompt, enter load install.
- From the Installation Options menu, select System Options and
press Enter.
- Select Edit STARTUP.NCF File and press
Enter. Add the following line to the STARTUP.NCF
file:
Set Minimum Packet Receive Buffers = 48
| Note: | Increase the minimum packet receive buffers by 48 for each additional adapter
that is installed.
|
- Press Esc and then answer Yes to save changes to the
STARTUP.NCF file.
- Select Edit AUTOEXEC.NCF File and press
Enter. Edit this file and, after the IPX internal net
statement, include the following statements. (Replace
C:\SERVER.312\ with the location of the NetWare server
program.)
In a server environment, set the DataRate to M16 or M4, and clients to
Auto. The default is Auto.
LOAD C:\SERVER.312\NBI31X
LOAD C:\SERVER.312\MSM31X
LOAD C:\SERVER.312\TOKENTSM
LOAD C:\SERVER.312\IBMTOKEN NAME=IBMLS1 DATARATE=M16
BIND IPX TO IBMLS1 NET=<unique net number>
See Novell NetWare Server Driver Parameters for a complete list of parameters that can be specified on
the LOAD IBMTOKEN command in the AUTOEXEC.NCF file.
Press Esc and then answer Yes to save the new file to
disk. Press Esc again to return to the server prompt.
- Shut down your server by entering down and then entering
exit from the server prompt.
- Enter server to restart the server.
- Installation is now complete. Shut down and restart your computer
for all changes to take effect.
Check for the following conditions to determine whether the adapter is
working correctly and whether installation is complete:
- The device driver files are loading successfully.
- There are no error messages.
If you experience problems, go to Appendix B. Problem Determination.
For information concerning NetWare server error messages, see Novell NetWare Server Driver Messages.
Before you start this installation, get the latest level of
patches for NetWare 4.11 Server from Novell. The current level
is IntraNetWare Support Pack Version 5.0 from the Novell support Web
site at support.novell.com. You will install the patches
during the following procedure.
If Novell NetWare is not on your computer, use the following
instructions. If it is on your computer, follow the instructions on
page ***.
Server Driver Installation in New NetWare 4.11 Server
Changes from the usual NetWare installation are necessary because this
driver is written to a new specification level that requires new NetWare
loadable modules (NLMs). The installation program is not aware of this,
though, and these NLMs must be loaded during installation of the server device
driver and after the server installation.
| Note: | A message referring to protected-mode BIOS access might appear before
installation of Novell patches. It is for information only, and can be
ignored.
|
- Create a diskette containing the extracted files from the
NETWARE.EXE package file on the IBM Turbo 16/4 Token-Ring PC Card 2
CD-ROM.
- When you see INSTALL Found the following: IBM Turbo 16/4 Token-Ring
PC Card 2 xxxx xxxx xxxx, press Enter. The actual
numbers vary by product. Then press the Insert (INS) key to
install the unlisted driver.
- Press ALT-ESC to toggle to the server console, and enter the
following LOAD statements (make sure that the diskette that you created in
step 1 is inserted in drive A):
LOAD A:\NOVELL\NETWARE\MSM.NLM
LOAD A:\NOVELL\NETWARE\TOKENTSM.NLM
- Press ALT-ESC to toggle back to the INSTALL panel.
- Press F3 on the next panel to specify A:\NOVELL\NETWARE
as the directory path.
Press Enter, then follow the instructions on the panel to
complete the installation of the driver. If you need to make any custom
configuration changes to the driver, do so at this time.
- Follow the instructions in the Novell manual to Create an
AUTOEXEC.NCF file. In addition to the instructions in the
manual, add the following lines to the AUTOEXEC.NCF file immediately
after the IPX INTERNAL NET statement (if necessary, replace C:\NWSERVER
with the location of the SERVER.EXE executable):
LOAD C:\NWSERVER\NBI.NLM
LOAD C:\NWSERVER\MSM.NLM
LOAD C:\NWSERVER\TOKENTSM.NLM
LOAD C:\NWSERVER\IBMTOKEN.LAN NAME=IBMLS1 DATARATE=M16
| Note: | There will be existing LOAD and BIND IPX statements in the
AUTOEXEC.NCF. Delete the LOAD statement (we have replaced it
with stated LOAD C:\NWSERVER\IBMTOKEN.LAN statement).
Also, make any needed modifications to the existing BIND IPX statement (refer
to the Bind the Protocol to the LAN Driver section of the Novell
manual for additional information).
|
See Novell NetWare Server Driver Parameters for a complete list of parameters that can be specified on
the LOAD IBMTOKEN command in the AUTOEXEC.NCF file.
- Press ESC and answer YES to save the new file to
disk. Press ESC again to return to the server
console.
- Type the following commands from the server prompt to shut down the server
and exit to DOS: down, then exit.
- Perform the following COPY commands, making sure that the diskette that
you created in step 1 is inserted in drive A. Note that it will prompt
you at each of the following files to ask if you want to perform a file
overwrite; it is OK to overwrite these files.
COPY A:\NOVELL\NETWARE\NBI.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\MSM.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\IBMTOKEN.LAN C:\NWSERVER
COPY A:\NOVELL\NETWARE\IBMTOKEN.LDI C:\NWSERVER
- Go to the Novell server directory and enter server at the DOS
prompt to restart the server.
- Install the latest available Novell patches for NetWare 4.11
now. Make sure to select the Version 3.31 ODI LAN Updates for
Hardware if given the opportunity.
- Issue the following commands from the server prompt to bring the server
down, then restart it: down, then restart
server.
- Installation is now complete. Check for the following conditions to
determine whether the adapter is working correctly and whether installation is
complete:
- The device driver files are loading successfully.
- There are no error messages.
If you experience problems, go to Appendix B. Problem Determination.
For information concerning NetWare server error messages, see Novell NetWare Server Driver Messages.
Server Driver Installation in
Existing NetWare 4.11 Server
If Novell NetWare is in your computer, perform the following steps to
install the adapter server device driver.
| Note: | If you are altering the configuration of a previously-loaded adapter, unload
that adapter before proceeding with these instructions.
|
- Create a diskette containing the extracted files from the
NETWARE.EXE file on the IBM Turbo 16/4 Token-Ring PC Card 2
CD-ROM.
- Be sure that your IBM Turbo 16/4 Token-Ring PC Card 2 is already in your
computer. If it is not, follow the instructions in Installation.
- Install the latest available Novell patches for NetWare
4.11. Make sure to select the Version 3.31 ODI LAN
Updates for Hardware if given the opportunity. Return to the server
console when the installation is complete.
- Down and restart server from the server prompt to
bring the server down, then restart it again.
- Check to see if the device driver is loaded. If it is, unload it
using the following command: unload token or unload
ibmtoken
- Type load install on the server.
- Select Driver Options.
- Select Configure Network Drivers.
- Select Select Drivers.
- On the next panel, press the Insert (INS) key to install the
unlisted driver.
- Insert the diskette that you created in step 1; press F3 on the
next panel and specify the path A:\NOVELL\NETWARE.
- Follow the instructions on the panels to complete the installation of the
driver. If you need to make any custom configuration changes to the
driver, do so at this time.
- Follow the instructions in the Novell manual to Create an
AUTOEXEC.NCF file. In addition to the instructions in the
manual, add the following lines to the AUTOEXEC.NCF file, immediately
after the IPX INTERNAL NET statement. If necessary, replace
C:\NWSERVER with the actual location of the SERVER.EXE
executable.
LOAD C:\NWSERVER\NBI.NLM
LOAD C:\NWSERVER\MSM.NLM
LOAD C:\NWSERVER\TOKENTSM.NLM
LOAD C:\NWSERVER\IBMTOKEN.LAN NAME=IBMLS1 DATARATE=M16
| Note: | There will be existing LOAD and BIND IPX statements in the
AUTOEXEC.NCF. Delete the LOAD statement (we have replaced it
with the stated LOAD C:\NWSERVER\IBMTOKEN.LAN statement).
|
Also, make any needed modifications to the existing BIND IPX
statement. Refer to the Bind the Protocol to the LAN Driver
section of the Novell manual for additional information.
See Novell NetWare Server Driver Parameters for a complete list of parameters that can be specified on
the LOAD IBMTOKEN command in the AUTOEXEC.NCF file.
- Press ESC and answer YES to save the new file to
disk. Press ESC again to return to the server
console.
- Type the following commands from the server prompt to shut down the server
and exit to DOS: down, and then exit.
- Perform the following COPY commands, making sure that the diskette that
you created in step 1 is inserted in the diskette drive. Note that it
will prompt you at each of the following files to ask if you want to perform a
file overwrite; it is OK to overwrite these files.
COPY A:\NOVELL\NETWARE\NBI.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\MSM.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\IBMTOKEN.LAN C:\NWSERVER
COPY A:\NOVELL\NETWARE\IBMTOKEN.LDI C:\NWSERVER
- Go to the Novell server directory and enter server at the DOS
prompt to restart the server.
- Installation is now complete. Check for the following conditions to
determine whether the adapter is working correctly and whether installation
has been completed successfully:
- The device driver files are loading successfully.
- There are no error messages.
If you experience problems, go to Appendix B. Problem Determination.
For information concerning NetWare server error messages, see Novell NetWare Server Driver Messages.
Server Driver Installation During NetWare 5.0
Server Installation
Installation of the network board and its device driver occurs during the
combined storage device and network board installation step. Use the
following instructions to install the network board and its driver during a
new NetWare 5.0 server installation.
- Create a device driver installation diskette.
Create a diskette containing the extracted files from the
NETWARE.EXE package file on the IBM Turbo 16/4 Token-Ring PC Card 2
CD-ROM.
- During the installation program, when you get to Select a Storage Device
and a Network Board:
- Select and configure the storage device
- Select and configure the network board
- Load a NetWare Loadable Module TM program (if required)
- Select a Storage Device
Storage devices such as hard disks, CD-ROMs, and tape devices require a
software driver to communicate with the storage adapter. The software
driver for the storage device is called a custom device module (CDM).
Each type of storage device requires a CDM.
The installation program auto-detects many types of storage devices such as
IDE drives, SCSI drives, CD-ROM drives, and tape drives. If your
storage device is not detected, choose the appropriate driver from the list of
available drivers provided with NetWare 5.0. You can also add a
new driver from a diskette. CDMs can be obtained from the storage
device manufacturer.
- Select a Network Board
The software driver for a network board is called a LAN driver.
The installation program auto-detects many types of network boards.
If your network board is not detected, choose the driver for the network board
from the list provided with NetWare 5.0. You can also use a new
or updated driver from the diskette that you created in step 1.
The network board must be installed and configured correctly. For
servers, it is recommended that DATARATE is set to M16 or M4, and clients be
set to Auto. You might be able to influence certain network board
properties by configuring the system and the network board or both.
- Load a NetWare Loadable Module (if required)
Certain server and network configurations might require you to load a
NetWare Loadable Module (NLM) before you can complete the server
installation. An example is loading ROUTE.NLM for a Token-Ring
environment that requires it.
Server Driver Installation in Existing NetWare 5.0 Server
The following procedure explains how to use NWCONFIG to load a LAN driver
and bind a protocol.
- Create a diskette that contains the extracted files from the
NETWARE.EXE package file on the IBM Turbo 16/4 Token-Ring PC Card 2
CD-ROM.
- At the server console prompt, enter NWCONFIG
- Select Driver Options > Configure network drivers.
- To select a driver from all of the available drivers, choose Select a
driver. The screen will display a list of all available
drivers.
- Press Insert. Follow the instructions on the
panels. Use the diskette that you created in step 1 when you are
prompted to supply an unlisted driver. The directory is
A:\NOVELL\NETWARE.
| Note: | For some drivers, a message might appear indicating that the driver must be
loaded manually (at the console prompt). To load a driver manually,
follow the screen prompts or press F1 for more information.
|
- Set protocols. When the window containing protocol choices is
displayed, select the protocol that you want to use and press the
spacebar. If you select TCP/IP, enter the IP address and the IP
mask.
- Set parameters. Use the down arrow key to move the cursor to the
parameter window. Enter parameter values as needed. Press F1 for
help. It is recommended for servers that the Data Rate is set to 4 Mbps
or 16 Mbps, and clients be set to Automatic.
In some cases, the system displays a pop-up list of values for the field
from which you select the desired value. In other cases, you must type
in a value and press Enter to move to the next field.
- To specify a particular frame type for a Token-Ring driver, press
F3 to display a list of frame types. Use the arrow keys to
move up and down the list. Press Enter to select a frame
type. When finished, press F10. If you do not specify
a particular frame type, all frame types are loaded automatically, but only
those found on the network are actually bound to the driver.
- Select Save parameters and load driver.
- Confirm bindings of the protocol with the driver and the network
number.
- Driver installation is now complete. To add another adapter, down
the server, power off the server, and insert the additional adapter.
NetWare will load the appropriate driver automatically. Then repeat
step 10.
- Download Novell Client DOS/Windows 3.1x Version 2.5 or
higher from the Novell Web site (support.novell.com).
Unzip the downloaded file to a directory on your computer.
- Exit Windows.
- From a DOS prompt, go to the driectory where you put the file. Run
INSTALL.EXE.
- Select Yes or No to respond to the Novell License
Agreement.
- Select Novell Client Windows Support and Work Station
Manager 3.X. Press F10 to save and
continue.
- Select 32-bit LAN Drivers and press F10 to
save and continue.
- Select USER SPECIFIED 32-Bit Driver and press
Enter. Insert the CD-ROM or the diskette that contains the
device drivers into the appropriate drive. Enter the path to the
32-bit ODI driver: x:\novell\netware where x is
your CD-ROM drive letter. The panel should say
IBM Token-Ring PCMCIA
Press Enter, configure the parameters, and press F10
to save and continue.
- At the Installation Configuration Summary panel, confirm that the values
are what you selected, and press F10 to save and continue.
- The files will be copied at this point.
- Installation is now complete.
- Reboot your computer and start Windows to connect to and login to your
server.
- Check for the following conditions to determine whether the adapter is
working correctly and whether installation has been completed
successfully:
- The device driver files are loading successfully.
- There are no error messages.
If you experience problems, go to Appendix B. Problem Determination.
(Previous version is IntranetWare Client for Windows 95.)
| Note: | You will need the Windows 95 diskettes or CD-ROM to complete this
installation.
|
If you are installing on a workstation that already has Windows 95
installed using Novell IntranetWare Client Version 2.2 for Windows 95,
use the following procedure.
| Note: | IntranetWare Client Version 2.2 for Windows 95 or Novell Client
Version 2.5 for Windows 95 can be downloaded from Novell on the Web at
support.novell.com
|
If you are upgrading from the NetWare DOS Requester (VLM) client or if you
do not have any network client installed, you need to have the Windows 95
CD-ROM or diskettes or the Windows 95 .CAB files.
- If the NDIS driver is not already installed, install it using the
instructions in Windows Installation.
- After downloading the code, run the installation program
(SETUP.EXE) for Novell IntranetWare Client Version 2.2 for
Windows 95 or Novell Client Version 2.5 for WIndows 95.
- Select Yes or No to respond to the Novell License
Agreement.
- Select Start to begin the installation.
If you are prompted to select an adapter, select one that matches your
hardware. This step might not be necessary, as you should have already
selected the adapter in the first step.
- If you do not need to customize your installation, select
Reboot.
- If you want optional features or need to configure your workstation,
select Customize. Then select Reboot.
For the Novell NetWare server, the parameters are set on the command line
or on the load IBMTOKEN line in the AUTOEXEC.NCF
file.
Table 4. Novell NetWare Driver Parameters
| Parameter
| Explanation
|
| DATARATE=
| Configures the Token-Ring data rate for the PC Card. It is
recommended for servers that the DATARATE be set to M16 or M4, and clients be
set to AUTO.
Valid values:
- AUTO
- AutoSense - automatic ring-speed detection.
| Note: | The PC Card will not function with AutoSense if it is the first one on the
ring. AutoSense is not designed for changing ring speed while the PC
Card is operational. It is usually necessary to reload the
driver.
|
- M16
- 16-Mbps ring speed operation.
- M4
- 4-Mbps ring speed operation.
The default is AUTO.
| Note: | If using Novell NetWare SFTIII, M16 or M4 must be selected for the DATARATE
parameter on both of the SFTIII machines. Do not use AUTO.
|
|
| FRAME=
| This string defines the frame type to be used with the PC Card when
loading the IBMTOKEN LAN driver.
Token-Ring drivers can add most-significant bit (MSB) or least-significant
bit (LSB) following the frame type designation. LSB forces canonical
addresses to be passed between the MLID and the upper layers. The MSB
designation forces non-canonical addresses to be passed (this is the default
for Token-Ring media).
- Valid values:
- TOKEN-RING or TOKEN-RING_SNAP
The default is TOKEN-RING.
|
| FULLDUPLEX=
| This keyword permits the IBMTOKEN LAN driver to activate Token-Ring
full-duplex operation supported by the PC Card and the NetWare server
environment.
- Valid values:
- YES, NO
The default is YES.
|
| MEM1=
| The MEM1 keyword is needed if you are using a Card Services version
earlier than version 5.00. This value is the base shared RAM
address that your adapter is configured to use. If it is not specified,
you will be prompted for this parameter when the driver loads. If you
are using a version of Card Services which is 5.00 or higher, this
parameter is not needed..
- Valid values:
- C0000, C4000, C8000, CC000, D000, D4000, D8000, DC000
There is no default for this parameter.
|
| NODE=
| This keyword is used to set a locally administered address for the PC
Card. A local address must contain 12 hexadecimal characters and can be
specified in either most-significant bit (MSB) or least-significant bit (LSB)
format.
To specify an MSB node address, the letter M immediately follows the last
digit of the node address. To specify an LSB node address, the letter L
immediately follows the last digit of the node address. If neither an M
nor L is specified after the last digit of the node address, MSB will be
assumed.
If a node address is specified in MSB format, the value must be within the
range X'400000000000' to X'7FFFFFFFFFFF' (for example,
X'400000000002'M). This same address specified in LSB format
would be X'020000000080'L with an L optionally appended to the
end.
Notes:
- Do not assign the same local address to two or more stations.
Severe station communication or network failures can occur when two or more
stations are assigned the same address.
- If you do not assign a locally administered address, the PC Card uses the
universally administered address permanently encoded in its memory.
|
| SLOT=
| This keyword defines the slot number of the corresponding PC Card in the
computer. To avoid being prompted to enter a slot number when the
IBMTOKEN LAN driver is loaded, specify this keyword. One SLOT number is
required for each NIC if you are using more than one.
|
| RT=
| Route Switching Mode. This parameter indicates whether the driver
should enable code that attempts to send routable traffic directly to a
destination rather than through the router. This can improve the
performance of these connections and reduce the workload at the router.
If the value is Disable, all routable frames will be sent through the
router.
Valid values:
- A
- Automatically determines whether to use Peer or Client mode.
- P
- Communicates with a peer destination station to establish a direct
path.
- C
- Uses an MSS server to determine the direct path.
- D
- Deactivates the route switching function for this PC Card.
The default is D.
|
| RTTS=
| Route Switching Table Size. This parameter specifies the number of
entries allowed in the route table kept for Route Switching support.
This should be set equal to or greater than the number of remote stations this
station will send data to using routable IP frames. If it is set too
low, some of the traffic that could be sent directly will instead be sent
through the router.
Valid values: 16-1024
The default is 1024.
|
| RTSM=
| Route Switching IP Subnet Mask. This parameter contains a
character string specifying the IP subnet mask for the IP subnet to which this
PC Card will attach. This value is entered as an IP dotted-decimal
value (for example, 255.255.255.0). This is a
mandatory parameter when the RTSWMode parameter is set to Auto or Peer.
Valid values:
- xxx.xxx.xxx.xxx
- A dotted-decimal IP network number (15 characters maximum).
- Disable
- When not in use.
The default is Disable.
|
| RTHT=
| Route Switching Holding Time. This parameter specifies the Route
Switching information holding time value. This determines how often a
remote station must refresh its Route Switching information which pertains to
this station.
Valid values: 2 to 20
The default is 20.
|
| TPRn=
| TCP Port Range. This represents a set of parameters which
designate the transmit frame priority value for a specified TCP port
range. n is 1, 2, 3, 4, or 5. The format of this 9-digit
hexadecimal string is:
<PortNumber><PortNumber><PriorityValue>
where each PortNumber is a four-character hex value and PriorityValue
is a one-character hex value. The two PortNumber fields define a
starting and ending value that make up a range, with the starting value less
than or equal to the ending value.
Valid values:
- PortNumber
- 0x0000 to 0xFFFF
- PriorityValue
- 1 to 6
There is no default for this parameter.
|
| UPRn=
| UDP Port Range. This represents a set of parameters which
designate the transmit frame priority value for a specified UDP port
range. n is 1, 2, 3, 4, or 5. The format of this 9-digit
hexadecimal string is:
<PortNumber><PortNumber><PriorityValue>
where each PortNumber is a four-character hex value and PriorityValue
is a one-character hex value. The two PortNumber fields define a
starting and ending value that make up a range, with the starting value less
than or equal to the ending value.
Valid values:
- PortNumber
- 0x0000 to 0xFFFF
- PriorityValue
- 1 to 6
There is no default for this parameter.
|
- Insert the IBM Turbo 16/4 Token-Ring PC Card 2 in your computer and switch
it on. When Windows loads, it will alert you to the fact that new
hardware was found in your computer. If it does not, see Troubleshooting and Error Codes.
- When the Update Device Driver Wizard (Windows 95) or the Add New Hardware
Wizard (Windows 98) appears, insert the CD-ROM or diskette that contains the
driver files.
- Follow the instructions on the panels to install the driver files for the
IBM Turbo 16/4 Token-Ring PC Card 2. During installation, you might be
prompted to insert the diskette labeled IBM Shared RAM Token-Ring Adapter NDIS
3/4/5 Device Drivers. At this point, click OK and select the
path to the driver diskette or CD-ROM in the copy files from box. You
might also be prompted to insert the diskette labeled Windows 95/98. At
this point, click OK and select the path to the diskettes, CD-ROM,
or hard disk where the Windows installation files are located in the copy
files from box.
- When driver installation is complete, Windows will prompt you to reboot
your computer. The IBM Turbo 16/4 Token-Ring PC Card 2 will not
function until you do so.
Some portable PCs that have support for Cardbus PC Cards use the Texas
Instruments Cardbus socket controller. Windows 95 OSR2 (build
4.00.950B) includes support for the chipset. IBM
Token-Ring PC Cards will not function correctly if:
- Your portable PC uses the Texas Instruments Cardbus controller chipset and
- Your installation of Windows 95 OSR2 uses the Cardbus drivers that shipped
with Windows 95 OSR2
If you are having problems getting your IBM Token-Ring PC Card to function
and you suspect that you have the Windows 95 Cardbus socket controller drivers
installed, follow the procedures below to determine if you need the Windows 95
Cardbus socket controller driver patch.
- Right-click My Computer on the desktop and select
Properties. This will bring up the system control
panel.
- Check the version of Microsoft Windows 95. If the version is
4.00.950B, you are running OSR2 and should continue reading;
otherwise, you do not need the patch.
- Click the Device Manager tab in the system control panel and
check to see if you have the Cardbus Socket Controller devices installed by
expanding the PCMCIA socket section. If you do not have this device
listed, then you do not need the patch.
- Click Start and select Find -- Files or
folders...
- Search for the file cbss.vxd on the drive that contains your
Windows installation (usually C). When you find it, right-click the
cbss.vxd file and select Properties.
- Click the Version tab and check the version of the file. If the
version is 4.00.1111, then you are using the Cardbus socket
controller drivers that shipped with Windows 95 OSR2. Contact the
computer manufacturer to obtain a patch for the Cardbus controller for Windows
95 OSR2.
- Insert the IBM Turbo 16/4 Token-Ring PC Card 2 in your computer and switch
it on. When Windows NT loads, login to the computer and open the
control panel. Double-click Network.
- Click Add Adapter and select <Other> Requires disk from
manufacturer. At this point, Windows NT will prompt you for your
driver files. Select the path to your driver diskette or CD-ROM and
click OK.
- When prompted to choose the adapter, select IBM Turbo 16/4 Token-Ring
PC Card 2. After installation is complete, the adapter should
appear in the Installed Adapter Cards window.
- Select OK to close the network control panel. You might
be prompted to configure your protocols. Consult the documentation that
came with your operating system if you need help doing this. You will
also be prompted to reboot your computer. The IBM Turbo 16/4 Token-Ring
PC Card 2 will not function until you do so.
- Insert the IBM Turbo 16/4 Token-Ring PC Card 2 in your computer and switch
it on. When Windows NT loads, login to the computer and open the
control panel. Double-click the Network icon.
- Click the Adapters tab, then click
Add.... Click Have Disk and
specify the location to the driver files.
- When prompted to choose the adapter, select IBM Turbo 16/4 Token-Ring
PC Card 2. After installation is complete, the adapter should
appear in the Network Adapters list.
- Close the Network Control Panel. You might be prompted to configure
your protocols. Consult the documentation that came with your operating
system if you need help doing this. You will also be prompted to reboot
your computer. The IBM Turbo 16/4 Token-Ring PC Card 2 will not
function until you do so.
Windows 2000 includes built-in support for your IBM Turbo
16/4 Token-Ring PC Card 2. Windows 2000 will automatically install its
built-in driver for you. However, the driver that comes with the
adapter includes support for some features that are not supported in the
driver that is included with Windows 2000. You might want to update the
driver to take advantage of the latest features.
- Click Start, Settings, and Control
Panel.
- Double-click System, select the Hardware tab, and
select Device Manager.
- Expand the network adapters, double-click IBM Turbo 16/4 Token-Ring
PC Card 2, and select the Driver tab.
- Select Update Driver, and follow the instructions on the panels
in the wizard.
- When the system says search for a suitable driver for my
device, insert the diskette, and specify the diskette drive
(a:\). Press OK.
- Follow the instructions on the panels until the installation is
complete. You might be alerted to the fact that the device driver has
not been digitally signed by Microsoft. Choose Yes to continue
installation. If your system is set up to block installation of
unsigned drivers, contact your system administrator for assistance.
- Restart your computer.
- Installation of the driver is now complete.
Instructions are on the adapter CD-ROM and can be read with
your Web browser. See Appendix A. CD-ROM Content and Software Packages.
If your OS/2 network operating system has not yet been installed on your
computer, install it now and follow its instructions for installing device
drivers. If an OS/2 network operating system has previously been
installed, follow the instructions here for using MPTS to install device
drivers.
- Start MPTS by performing either of the following actions:
- From the OS/2 desktop, double-click the MPTS icon.
- From an OS/2 window, go into the IBMCOM subdirectory and enter
mpts at the OS/2 prompt.
- Select OK on the MPTS logo panel.
- Select Install. You will be prompted for the source of
the .NIF file. Put the CD-ROM in the drive. Enter
x: where x is the letter of your CD-ROM drive. Select
OK once the Installation Complete message appears. You will
return to the main menu.
- Select Configure in the MPTS dialog box.
- On the Configure panel, make sure that LAN adapters and
protocols is preselected and then select Configure at the
bottom of the panel.
- In the Configuration panel, in the Network Adapters group box, select
IBM Turbo 16/4 Token-Ring PC Card 2 and select
ADD.
| Note: | You can edit parameter settings for this PC Card. Highlight this
adapter in the Current Configuration list box and select
Edit. When you have finished with the parameter settings,
select OK.
|
- In the Protocols list box, select the protocols used by your network
application. Highlight each protocol and select ADD.
If you are not sure which ones to use, select IBM IEEE 802.2
and IBM OS/2 NetBIOS protocol drivers or ask your network
administrator.
The protocol drivers you have selected will appear under the adapter driver
name in the Current Configuration list box.
| Note: | You can edit parameter settings for the protocols. Highlight a
protocol and select Edit.
|
- Select OK when you have finished selecting and editing
protocols in the Configuration panel.
- Select Close on the Configure panel.
- Select Exit in the MPTS dialog box.
- Select Exit on the Update CONFIG.SYS panel to update the
CONFIG.SYS file.
- Select OK when you get the message that the CONFIG.SYS
has been successfully updated.
- Select Exit on the Exiting MPTS panel.
- Shut down OS/2 and restart your computer to let the changes take
effect. Installation is now complete.
- At system startup, check for the following conditions to determine whether
the adapter is working correctly and whether installation has been completed
successfully:
- The device driver files loaded successfully. There are no error
messages.
- You are able to log on and communicate with the network.
If you experience problems go to Appendix B. Problem Determination.
IBM TCP/IP for OS/2 is an example of a product that provides driver
installation programs.
- Insert the CD-ROM in the drive.
- Use your product documentation to install the driver
(IBMTOKCS.OS2).
- Change the parameters if needed.
- Installation is now complete. Shut down and restart your computer
for all changes to take effect.
- Check for the following conditions to determine whether the adapter is
working correctly and whether installation has been completed
successfully:
- The device driver files load successfully.
- There are no error messages.
If you experience problems go to Appendix B. Problem Determination.
Perform the following installation steps for the PC Card to install a real
mode driver when using Microsoft Windows for Workgroups:
- Follow the setup instructions included with Windows for Workgroups.
If Windows for Workgroups is not already installed, you will be prompted to
install a network PC Card during the Windows for Workgroups installation
process.
If you are installing the PC Card in a computer that already has Windows
for Workgroups installed, refer to the Microsoft
Windows for Workgroups User's Guide for instructions on how to install and configure a third-party device
driver.
| Note: | If you have Windows for Workgroups Version 3.11, perform the following
steps before proceeding with step 1.
- When you get to the Network Setup window, select Networks, and
then Install Microsoft Windows Network.
- Change any other items for your environment, and select OK and
Continue.
- When prompted to install a new PC Card, select Unlisted or
updated network adapter. You will be asked to provide the network
driver. Insert the CD-ROM, check the path, and select
OK.
- Follow the instructions as they appear on the window to install the
IBMTOKCS.DOS device driver.
- Accept the defaults for Interrupt, MMIO, and SRAM. You will be
given a chance to update these later, if necessary.
- Exit the Windows for Workgroups setup. Do not reboot
your computer at this time. Exit to the DOS prompt.
|
- Configure the PC Card.
Memory management notes
- If you are using Card and Socket Services, the program will default to
Autoset mode, which allows the LAN driver to negotiate with Card and Socket
Services for available resources. LANAID will allow you to select
values for resources to be used by your PC Card such as Interrupt, memory, and
I/O Base Address.
- If you are not using Card and Socket Services in Autoset mode, you must
ensure that the values that you select for Interrupt, MMIO, and SRAM do not
conflict with those for other PC Cards and resources installed in your
computer (such as video, sound, COM port).
- If you are using EMM386, in most cases the memory exclusions will be
automatically handled by LANAID. If you are using a memory manager, you
must exclude the memory ranges being used by your PC Card (8-KB
default).
- If LANAID is not already installed, install it as described in Installing LANAID.
- After LANAID is installed, continue with Using LANAID to Configure the PC Card. When you get to the panel that asks for the existing
network operating system, select Microsoft Windows for
Workgroups.
- Step 5 of the Installation Checklist is now complete.
Continue with the next step on page "Checklist".
| Note: | It is recommended that you use LAN Client (Client32) whenever possible as an
efficient solution.
|
The 16-bit DOS Novell NetWare Requester environment supports access
to servers running Novell NetWare 3.11 or higher.
To install the TOKENCS.COM ODI driver on a DOS computer, perform the
following steps. Consult your Novell NetWare documentation for
instructions regarding how to create the NetWare Client for DOS and MS Windows
diskettes.
- Create a diskette containing the extracted files from the
DOSODI.EXE file on the IBM Turbo 16/4 Token-Ring PC Card 2
CD-ROM.
- Insert the NetWare Client for DOS and MS Windows Disk 1 into the
appropriate drive.
- At the command prompt, type a:, where a is your drive
letter, and then press Enter.
- Type install and then press Enter.
- Follow the instructions as they appear. In step 5 of the
instructions, press Enter and select Other
Drivers.
- Insert the CD-ROM or the diskette that you created in step 1 into the
appropriate drive. When prompted, specify the location to the chosen
media and press Enter. Specify the path as
a:\novell\dos (or x:\novell\dos for the
CD-ROM version).
- Highlight your adapter and press Enter.
- At this time you can change the default parameters. When you finish
making any desired changes, press F10. ODI 16-bit Client Parameters contains the parameters that can be configured in the
NET.CFG file.
- Follow the instructions presented to finish the installation.
| Note: | If source routing is required, edit the STARTNET.BAT file that is in
the client directory (usually c:\nwclient) and add the following line
after the IPXODI statement.
c:\nwclient\route
|
- Shut down and restart your computer for all changes to take effect.
- Check for the following conditions to determine whether the adapter is
working correctly and whether installation has been completed
successfully:
Table 5. ODI 16-bit Client Parameters
| Parameter
| Explanation
|
| NODE ADDRESS
| To set a locally administered address for the adapter, type in the local
address that you want to use. The local address must contain 12
hexadecimal characters and can be specified in either MSB (the default), or
LSB format. To specify an MSB node address, the letter "M" immediately
follows the last digit of the node address. To specify an LSB node
address the letter "L" immediately follows the last digit of the node
address.
This keyword is specified as NODE ADDRESS in NET.CFG for DOS and
OS/2 workstations.
If a node address is specified in MSB format, the characters must be within
the range X'400000000000' -- X'7FFFFFFFFFFF'. To
specify a node address in MSB format, add an "M" to the end of the address
(for example, X'400000000000M'). This address specified in LSB
format would be X'020000000080L'.
Notes:
- Do not assign the same local address to two or more stations.
Severe station communication or network failures might occur when two or more
stations are assigned the same address.
- If you do not assign a locally administered address, the adapter uses the
universally administered address (the address encoded in the adapter memory at
the factory). The universally administered address appears on a label
on the adapter.
|
| PORT
| The port address for a primary network adapter is X'A20'.
The port address for an alternate network adapter is X'A24'.
- Valid values:
- X'A20' and X'A24'
- Default value:
- X'A20'
|
| NIC UAA
| This parameter can be used to specify which physical network adapter is
to be associated with this load of the LAN driver. The parameter value
can be a 1-digit ordinal value or a 12-digit, hexadecimal,
universally administered address (MAC address).
With ordinal type parameter usage, an ordinal value of 1 indicates the
adapter with the lowest universally administered address
value. An ordinal value of 2 indicates the adapter with the next lowest
universally administered address, and so on. If there are two adapters,
the one with the higher MAC address has an ordinal value of 2.
This parameter is not required for a single network adapter; however, this
parameter is necessary if the system contains more than one network adapter
and at least one of them is a Turbo 16/4 Token-Ring PC Card 2.
Otherwise, system or network errors are likely to result.
|
| NOFULLDUPLEX
| This parameter disables full-duplex ring insertion.
|
| MAX FRAME SIZE
| This option sets the maximum number of bytes that can be put on the wire
by the Turbo 16/4 Token-Ring PC Card 2. The number must be a multiple
of 8 and include the number of bytes for the data packet for adapter overhead
(6 bytes) and for the maximum header (35 bytes LAN header + 5 bytes SNAP
header + 74 bytes protocol header). The total number of bytes is
114.
If the LAN speed is 16 Mbps, the number must be between 632 and 17
960. If the LAN speed is 4 Mbps, the number must be between 632 and 4
464. If 2 KB packets are desired, calculate the maximum frame size
as:
2048 + 6 + 35 + 5 + 74 = 2168 (rounding up to next multiple of 8 gives
2168)
An example NET.CFG entry for using 2-KB packets would appear
as:
LINK DRIVER TOKEN
MAX FRAME SIZE 2168
In an OS/2 environment, to set frame sizes greater than 1540 bytes, you
must configure LSL buffers equal to or greater than the frame size you
desire. To configure the adapter to handle 4210-byte frames, use
this statement in your NET.CFG file:
LINK SUPPORT
BUFFERS 14 4210
Refer to the section that discusses NET.CFG options in Novell
NetWare Workstation 4.0 for OS/2 for information about
configuring link suport layer buffers.
|
| FRAME
| This parameter indicates the token-ring frame type to be used by the LAN
driver and network adapter.
- Default value:
- Token ring
- Valid values:
- Token ring, token-ring_SNAP
|
| NOSHALLOWMODE
| This parameter disables adapter shallow mode operation.
|
| RECEIVEBUFFERSIZE
| This parameter can be set to a value from 192 to 2048, inclusive.
Any value smaller than 192 is changed to 192. Any value larger than
2048 is changed to 2048. Numbers between 192 and 2048 that are not on
an eight-byte boundary are rounded up to the next higher eight-byte
boundary.
|
| EXPRESSMODE
| For DOS only, this parameter enables adapter fast-path receive express
mode.
|
| ENHANCEDMODE
| Causes the adapter to operate in fast-path receive mode and in the
4-KB paging mode of fast-path transmit operation. The Auto 16/4
Credit Card can not function in Enhanced Mode (Enhanced=NO).
|
| BUS ID PCMCIA 3
| This keyword must be present in the NET.CFG file.
|
| PCMCIA
| This keyword must be present in the NET.CFG file for
configurations that use Card Services to enable the adapter. This
keyword must not be used in configurations that enable the adapter by way of a
Point Enabler.
|
| AUTORINGSPEED
| This keyword will cause the adapter to save the speed of the ring that it
is opening into and use that ring-speed value as its speed the next time that
it is initialized.
|
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]